3 subject="""comment 4"""
4 date="2023-09-07T18:36:37Z"
6 Another related case is when git has been configured with
7 safe.bareRepository=explicit and the remote (either ssh or local)
8 is a bare repo. git-annex-shell will fail with the same misleading message,
9 and for a local repo, git-annex will also display the same misleading
12 I think it also ought to override safe.bareRepository for such remotes,
13 because eg git pull works with such remotes. The point of
14 safe.bareRepository=explicit is not to prevent using bare remotes, but to
15 prevent things like shell prompts to accidentially use bare repos that are
16 eg, committed by a malicious attacker to a git repository, to avoid using
17 git configs that allow running arbitrary code.